Index
> Projects and Ideas > Asm driven CMS.Goto page Previous 1, 2, 3, 4, 5 Next |
| Author |
|
|
JohnFound 02 Jun 2012, 15:54
revolution wrote: Clearly I was unable to convince you that menu driven webpages are a bad idea and reduce usability. Well, I don't think so. The tree menu allows user to browse only the part of the information, but in the same time to have clear picture of the whole. This approach actually increase usability. Not for nothing, all applications that need to display big amount of items, tent to use some hierarchical presentation of the lists and to use tree view display. What is your idea for the best navigation method in the site with big amount of pages? _________________ Tox ID: 48C0321ADDB2FE5F644BB5E3D58B0D58C35E5BCBC81D7CD333633FEDF1047914A534256478D9 |
|||
02 Jun 2012, 15:54 |
|
|
shutdownall 03 Jun 2012, 00:27
JohnFound wrote:
Well - what does Google do to let the people browse in the big database ? A (indexed) search function.  |
|||
|
03 Jun 2012, 00:27 |
|
|
JohnFound 03 Jun 2012, 03:50
Search is not navigation. It is different function.
|
|||
|
03 Jun 2012, 03:50 |
|
|
Enko 03 Jun 2012, 05:21
I think it's a preaty good aproach. Similar to msdn, but without the frames, more original, same usage.
|
|||
|
03 Jun 2012, 05:21 |
|
|
shutdownall 03 Jun 2012, 10:53
JohnFound wrote: Search is not navigation. It is different function. This is just your point of view. Search is a valid method of navigation. Even if you have large databases, a general navigation may not make sense under all conditions. For example, if you have a telephone book, you could try to find navigation criteria by name beginning with first letter oder by street or even by number for reverse search. The point is, that the customer may find your structure not convenient for HIS point of view. A (good) search function is more flexible, more than a standard navigation ever could be. But it's really dependend on your data. But you asked for big amount of pages whatever is big for you. Maybe maybe thousand, maybe million. |
|||
|
03 Jun 2012, 10:53 |
|
|
JohnFound 03 Jun 2012, 13:25
There definitely will be implemented search engine for MiniMagAsm. But not for version 1.0, unless someone wants to implement it.
|
|||
|
03 Jun 2012, 13:25 |
|
|
edfed 05 Jun 2012, 19:13
the asm database engine is comming to be a need now
i work a little on mysql db, and the records seems to be a ugly shit, as long as the .db file is growing, the requests become really slow, inducing some "dangerous" operations like periodic depository, hard dirve use intensive, more than tens of thousands writes per hour. meaning the hard drive will see his life shortened, and making usb or ssd drive completelly unusable for this purpose. imagine a usb boot with all the "website" onto, it will die in less than some hours. then, need a good database engine, in asm of course. |
|||
|
05 Jun 2012, 19:13 |
|
|
JohnFound 05 Jun 2012, 19:27
edfed, you should try SQLite. It is not server database, but it is really small and pretty fast. (well, as fast as SQL RDBE can be).
Actually it is the only database engine, that worth to be used with assembly projects. But you are right - good assembly database will be great. If we have to write a wish list, there will be hundreds of programs that need to be rewritten from scratch in assembly. Good vector drawing editor, good office package, web browser, database engine, etc. etc. |
|||
|
05 Jun 2012, 19:27 |
|
|
Enko 05 Jun 2012, 19:59
In my work, I have a little php program for controling service orders. I use easyPhp 1.8 (really old version)
It has an old version of mysql, where the BIN folder is 6.85MB, and i never had any problem at all. The DATA folder of the datebase is 30mb, explorted the datebase it hase 8000 entries in the main table and its only 500kb ziped. Of course it´s a single user application, so I can´t tell about the real load. |
|||
|
05 Jun 2012, 19:59 |
|
|
JohnFound 05 Jun 2012, 20:08
SQLite is 500KB single DLL. But even 500KB library is too big if you use it with 50KB assembly program (what is a big project for assembly).
|
|||
|
05 Jun 2012, 20:08 |
|
|
Enko 05 Jun 2012, 20:20
Do you save all your projects on a floppy disk?
And I don´t talk about a 3" 1/4, but a 5" 1/2 with the B face broken. xD Code: JFsql>SELECT * FROM miniMagAsm WHERE TITLE LIKE 'fasm'; JFsql>QUERY PERFORMED IN 2MS, data not found. Insert disk 2A JFsql>READING FLOPPY. FETCHING DATA. PERFORMED 1min JFsql>QUERY PERFORMED IN 2MS, data not found. Insert disk 2B JFsql>READING FLOPPY. FETCHING DATA. PERFORMED 1min JFsql>QUERY PERFORMED IN 2MS, data not found. Insert disk 3A JFsql>READING FLOPPY. FETCHING DATA. PERFORMED 1min JFsql>QUERY PERFORMED IN 2MS, data not found. Insert disk 3B JFsql>ERROR: DISK CORRUPTED JFsql>data not found. NO MORE DISK AVAIBLE JFsql>QUITE I know what you wan´t to say, but to have to write a real universal database engine and make it stable is a really hard work using any compiler/assembler. |
|||
|
05 Jun 2012, 20:20 |
|
|
JohnFound 05 Jun 2012, 20:51
It was edfed's idea not my.
I plan a web browser, but have no enough free time.  |
|||
|
05 Jun 2012, 20:51 |
|
|
edfed 06 Jun 2012, 09:06
i think a assembly database engine should not be made around a single file, but on a file system tree, each table being a folder, discomposed in 512 bytes (or 512^n bytes) elements.
then, it will force to improve the file system access and structure, and then, the hard drive access, that will give a really good file system, and a very simple database engine over that. i think it is important to limit the number of layers before to reach the usefull datas when dealing with assembly. means that a file system should be designed especially for assembly programming, with structures closer to the hardware than what we can find in current file systems. technically, the sectors for a single table, or a single database should be in a linear adress space, translated to LBA, and transparent when used in ram or in drive. i am currently working on it (since 2006 now ) and it my version will be based on fool structures. |
|||
|
06 Jun 2012, 09:06 |
|
|
Enko 14 Jun 2012, 22:36
I´ve seen the last updates, the logo looks better xD
And the site renders wonderful |
|||
|
14 Jun 2012, 22:36 |
|
|
JohnFound 14 Jun 2012, 23:12
Enko wrote: I´ve seen the last updates, the logo looks better xD I am glad you like it.
The CMS is now almost finished, at least in its first version. I am trying to use fossil for version control of the articles, but have some troubles with it. Also, the markdown parser needs some more work. _________________ Tox ID: 48C0321ADDB2FE5F644BB5E3D58B0D58C35E5BCBC81D7CD333633FEDF1047914A534256478D9 |
|||
|
14 Jun 2012, 23:12 |
|
|
Enko 16 Jun 2012, 00:41
JohnFound, I was looking for a fasm cgi example on linux and found this post
http://board.flatassembler.net/topic.php?t=14234 
You grow up very fast. |
|||
|
16 Jun 2012, 00:41 |
|
|
JohnFound 16 Jun 2012, 03:55
Ah,yes. I remember this thread. Actually it triggered the development of MiniMagAsm.
But I didn't purchased the hosting. I set my own server up. (I am proud of myself - 26 days up now) So, did I grew up? |
|||
|
16 Jun 2012, 03:55 |
|
|
Enko 16 Jun 2012, 13:33
Quote: So, did I grew up? No. You cheated like Peter Pan. ^^ |
|||
|
16 Jun 2012, 13:33 |
|
|
JohnFound 17 Jun 2012, 12:28
Added "Edit page" function - look at the end of the main menu.
It still can't save the edited file to the disk, but it works in "preview" mode. The engine will render the edited page without saving it to the disk. So, the visitor now can play with the MiniMagAsm markup language in order to check its features and simply for fun. Later I will implement the password protected features for creating new articles, deleting the old one and saving the changes to the server disk. |
|||
|
17 Jun 2012, 12:28 |
|
| Goto page Previous 1, 2, 3, 4, 5 Next < Last Thread | Next Thread > |
Forum Rules:
|