![]() |
|
#1
|
||||
|
||||
GIM gidedit - a fltk fluid resize projectHey all,
I have been playing with the old pedit app that dsmith posted a while back. As a start I wanted to define the base for the app and control the resize behavior before even getting into the real app itself. I think I have it under control (finally) and have simply defined the group areas that will make up the main UI. Any of the subclasses will replace the existing groups. For now there is a group that will be the menubar, a group that will be the empasis, a group that will be the links, a group that will be the markups, a group that will be the smilies, a group that will be the editor proper, and an output group that will be messages. Code:
Right now, the groups have visability so you can see the action of the resize. I think it works the way I want. I will post more (at the very least a mock-up of the filled button bars) as it gets completed. As it sits, all the button bar groups and output group maintain their vertical size while allowing the horizontal size to be modified. Pretty simple really. Mark The attached screen shots show the default open, minimum resize and large resize. __________________
"Opportunity is missed by most people because it comes dressed in overalls and looks like work." --Thomas Alva Edison "Those who would give up essential liberty to purchase a little temporary safety, deserve neither liberty nor safety." --Benjamin Franklin "A happy person is not a person in a certain set of circumstances, but rather a person with a certain set of attitudes." --Hugh Downs |
|
#2
|
||||
|
||||
|
Very nice...
Is the large size the "maximum" size or is it just a large size? And I assume the full screen would resize properly as well. That post editor (pedit as I called it) would be a good thing to have IMO. Like most things that I do, it was just kind of thrown together, but with a bit of help I think that we could make that into a very valuable tool. Not just for GIDForums™, but for any forum. However, other forums don't have C-mark up __________________
The best damn Sports Blog period. |
|
#3
|
||||
|
||||
GIMpeditThanks D. Yes, I just did a drag instead of a full screen. That has been fixed in this version.
I agree with you that a post editor that could handle markup would be a very cool tool, especially if you are like me and spend a large amount of time on a particular post. I could see it being useful if you are not from the cable generation as well (oh, I hear you dsl folks booing and hissing) and dialup for connectivity. Lastly, it should not just be for the fine GID folks but configurable to your favorite (there are others :gasp: ) forums. Ok, so another forum may not have cool code markups or the smilies may be different, etc, etc. That is the very reason I am trying to design the pedit app in a way that will take different specs for different boards. Now I personally wouldn't go anywhere else but... ![]() Ok, enough of that rot. When good ole' dsmith posted pedit I didn't even know that GID existed and GIM was not (AFAIK) even a public entity yet. I had never even heard of FLTK nor could I make a distinction between referring to a value by reference or address. Oh ain't time cool! Now I place a hunk of fluid project code (1.1.x or .7 as I refer to it as) that is a basic framework for pedit. Essentially, the frame describes the UI for a post editor. Even without use of fluid you should be able to deem what is what. There are seven distinct areas of the UI. Simply put,
Each of these (in my iteration anyhow) will be derived from an FLTK widget that inherits from a group. Because of this, any designed class can have its pointer tossed at the basic frame groups for display purposes. For now I have just defined some GID style buttons that show what can be done here. What I am really saying is that these groups will be subclasses that will state the specifics for that area. Here at GID the empasis markup is,
So the app itself should just need to poll the specific class, find out how many choices (and then the button label) and place them accordingly at the default size of 400X440. The resize behavior is based on the type of information that will be presented to the user so it should be trivial to adjust accordingly. An example of this is the exclusion of the size choice widget or the racking of the light buttons based on the assumption that if you can see two letters, you can use the buttons even at a minimal state. What I am looking for now is what bothers you about the UI. What about it doesn't work? Some things that come to mind are, "What if there are too many of a particular type of group members?" I guess doubling the height would be the answer. Well, here is the code and some pix to show how the resizing works. Enjoy. Code:
Hope you found this even vaguely interesting. Mark [edit] the fluid project file does not perfectly represent the attached images. I made some resizing adjustments while working on this post and now the smilie images are protected as well as changes to the output info area [/edit] __________________
"Opportunity is missed by most people because it comes dressed in overalls and looks like work." --Thomas Alva Edison "Those who would give up essential liberty to purchase a little temporary safety, deserve neither liberty nor safety." --Benjamin Franklin "A happy person is not a person in a certain set of circumstances, but rather a person with a certain set of attitudes." --Hugh Downs |
Recent GIDBlog
NARMY by crystalattice
| Thread Tools | Search this Thread |
| Rate This Thread | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| FLTK && fluid In Motion | cable_guy_67 | FLTK Forum | 4 | 20-Mar-2008 03:52 |
| [Tutorial] GUI programming with FLTK | dsmith | FLTK Forum | 10 | 03-Oct-2005 15:41 |
| Community Project Proposal | dsmith | Miscellaneous Programming Forum | 71 | 19-Feb-2005 12:26 |
| GIMcontacts - a gim fltk fluid venture | cable_guy_67 | FLTK Forum | 0 | 14-Feb-2005 14:18 |
| Simple FLTK dialog box sample | cable_guy_67 | FLTK Forum | 4 | 02-Nov-2004 08:46 |
Network Sites: GIDNetwork · GIDWebHosts · GIDSearch · Learning Journal by J de Silva, The