Menu
▾
▴
phpmyedit-discuss
|
From: Bruno B. \(Levure\) <le...@ba...> - 2002-10-28 14:46:12
|
Hello from Belgium, I'm deaf, and I would like to bring my tribute to the phpmyedit projet by adding : - A CSS generator to make CSS files to use with the generated PHP files (to gives the possibility to the user to changes easily the font, background, buttons appearance... - The possibility to have the details appearing in a popup box. How can I join the development team in order to publish the new files when I will have finished theses add ? (Don't worry, I will comment a lot my code !) Yours truly, ------------------------------------- Bruno BAGUETTE - le...@ba... |
|
From: Ondrej J. <ne...@po...> - 2002-10-29 19:31:42
|
Maxim, 20:08:41
29. oktober 2002 (utorok)
Greetings.
> - A CSS generator to make CSS files to use with the generated PHP files
> (to gives the possibility to the user to changes easily the font,
> background, buttons appearance...
This seems to be very good idea, but anyway before implementing we
should solve CSS classes generation policy for phpMyEdit. Every generated
element/object by phpMyEdit should have some particular class and it is
really for big thought, how they should be divided and how the names should
be.
I will appreciate your assistance in this issue. I recognize, that
all phpMyEdit CSS classes should have "pme_" or configurable prefix, and
there should be even/odd list table row difference, but I'm really unsure
about others generated HTML elements/objects (and their names).
> - The possibility to have the details appearing in a popup box.
Please, if it is possible, be more descriptive about this issue. I
completely do not understant an issue.
> How can I join the development team in order to publish the new files when
> I will have finished theses add ? (Don't worry, I will comment a lot my
> code !)
You can join development by using this mailinglist. Send patches of
files, or publish them on website. I will add them into CVS and they will
appear in further phpMyEdit distributions.
Thanks,
=Nepto=
____________________________________________________________________________
Ondrej 'Nepto' Jombik, http://www.nepto.sk/ ne...@at...
|
|
From: Bruno B. \(Levure\) <le...@ba...> - 2002-10-29 20:57:10
|
Hello ! I will send in a few minutes, a email about the CSS classes proposal ! :-) > > - The possibility to have the details appearing in a popup box. > > Please, if it is possible, be more descriptive about > this issue. I completely do not understant an issue. Ok, I will try to be more clear ! :-) When the generated file display a listing of the tuples from one table, it don't always display ALL the fields. We should add a "detail" button that display ALL the fields of one selected tuple inside a "popup" (one little HTML page) instead of displaying the details in the same window. In other terms, to give the possibility for the user to display the details of one tuple in a popup, and to keep the listing in the main windows. So, we have a new little window that appears with the details of the selected tuple. Am I clear enought ? :-) > You can join development by using this mailinglist. > Send patches of files, or publish them on website. I will add them into CVS > and they will appear in further phpMyEdit distributions. Ok, can I send attachment files in the mailinglist or do I have to paste the code inside the message ? Thanks for your welcomes to my proposals, I will try to help the team as much as possible ! :-) ------------------------------------- Bruno BAGUETTE - le...@ba... |
|
From: Ondrej J. <ne...@po...> - 2002-10-30 11:43:30
|
Maxim, 11:04:10
30. oktober 2002 (streda)
Greetings.
> > > - The possibility to have the details appearing in a popup box.
> > Please, if it is possible, be more descriptive about
> > this issue. I completely do not understant an issue.
> When the generated file display a listing of the tuples from one table, it
> don't always display ALL the fields. We should add a "detail" button that
> display ALL the fields of one selected tuple inside a "popup" (one little
> HTML page) instead of displaying the details in the same window.
None from my english dictionaries contain word "tuple". But I
suppose, that it is something like "record".
> In other terms, to give the possibility for the user to display the
> details of one tuple in a popup, and to keep the listing in the main
> windows. So, we have a new little window that appears with the details of
> the selected tuple.
> Am I clear enought ? :-)
Well, more clear. But what is the difference between this and view
functionality? You can turn on action icons (use $opts['navigation']) on
page. By clicking on view picture with opening in new window you will get
the same functionality as you have described.
> > You can join development by using this mailinglist.
> > Send patches of files, or publish them on website. I will add them
> > and they will appear in further phpMyEdit distributions.
> Ok, can I send attachment files in the mailinglist or do I have to paste
> the code inside the message ?
Small patches can be sent into mailinglist, bigger should be
published on website or they can be sent to me directly. ;-)
=Nepto=
____________________________________________________________________________
Ondrej 'Nepto' Jombik, perl -le '$_=1;(1x$_)!~/^(11+)\1+$/&&print while$_++'
|
|
From: Bruno B. \(Levure\) <le...@ba...> - 2002-10-29 20:57:30
|
Hello, On the proposal of Ondrej Jombik, I would like to begin a "brainstorming" about the setup of a CSS classes generation policy for PHPMyEdit. I think that all the phpMyEdit CSS classes should be prefixed with a configurable string which will have the default value of "pme_" (for PhpMyEdit). For example, in a listing, we should have three classes for the rows : HeaderRow : Class pme_row_headers Row 1 : Class pme_row_listing_one Row 2 : Class pme_row_listing_two Row 3 : Class pme_row_listing_one Row 4 : Class pme_row_listing_two Row 5 : Class pme_row_listing_one Row 6 : Class pme_row_listing_two This rotation between the two classes would bring more readability for large and long tables. I think there's two different kind of CSS classes in the case of the PhpMyEdit project. Some classes are common for several generated files, and somes classes are unique for one kind of generated files. We should begin by making a list of theses classes and build a table with the uses of theses classes. Do you agree with that ? If you agree I can begin to make the list of the currently used classes and to build a table with the uses of the CSS classes in the different kind of generated files. Kind regards, ------------------------------------- Bruno BAGUETTE - le...@ba... |
|
From: Ondrej J. <ne...@po...> - 2002-10-30 11:43:35
|
Maxim, 12:21:26
30. oktober 2002 (streda)
Greetings!
> On the proposal of Ondrej Jombik, I would like to begin a "brainstorming"
> about the setup of a CSS classes generation policy for PHPMyEdit.
Yesterday, late night I made long think about the issue and here are
my rough notes:
1. Basic CSS configuration will be using $opts['css'] array/hash.
2. We have at least following suboptions:
['prefix'] - default value is "pme_"
['dividor'] - well this should have better name, but it says how
many list table rows should have own number before
starting counting from 0; value of -1 means every row
has its own number
['buttons_pos'] - if the buttons should get their class name
according to possition on page name
(ie. pme_button_down)
['buttons_type'] - if the buttons should get their class name
according to type (ie. pme_button_search)
['buttons_func'] - similary functionality (pme_button_next)
If more from buttons_* option is turned on, the result class name
will be joined in one string. Example: pme_button_down_change.
3. Similar booleans (they should not be letter flags?) must have other
elements, such as <hr>, so ['hr_pos'] = true -> pme_hr_up, pme_hr_down
4. There are two types of screen: table listing and one record display.
5. There are three types of buttons:
- table list action buttons:
next, prev, add, view, delete, copy, change
- record display action buttons:
save, more, cancel, delete, [apply]
- search buttons:
search, hide, cancel, query
6. Every column can have new option ['css'] ($opts['fdd']['col']['css']).
7. Column ['css'] has:
['postfix'] - what to add to all classes that are connected with
this column (so its TH class will get this postfix,
also its filter input field, also its TDs); this will
allow us to have for example one col hightlighted with
different color what other cols; rather cool, isn't it?
This covers only part of whole problematic. Please feel free to
write your notes to described issue and/or some new ideas. They are welcome
and appreciated!
=Nepto=
____________________________________________________________________________
Ondrej 'Nepto' Jombik, Open Source software developer, http://www.platon.sk/
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X