I have several ideas. I would like to test them in practice to see how well they work.
1) I would like to render prints to separate area from the code area, so the user wont have to delete those prints to carry on coding. I dont know if an embeded inspector would make more sense in this case, with continuous tracking of values. 2) I would also like to render information like the super class of an object, class comment, implementors of a method, etc without having to open a system browser to do so from inside workspace. 3) Another thing is emac's like navigation around, move to next message, easy selection and generally the usual stuff one can do with emacs without having to use a mouse. 4) a History feature would also be cool, something that can track changes of a workspace and have different versions of a code. Probably there is already this feature , with the ability to recall past workspace but maybe I could polish it a bit. 5) Also I am interested in quick creation of methods and classes, select a piece of code in workspace and send it to a method directly again completely bypassing the system browser and preferably not having to pop up dialog messages. 6) Embedding widgets like sliders and knobs for quickly changing values with the mouse could be nice as well. Going to study the Moose playground as well to see how you guys hack the workspace. On Mon, May 19, 2014 at 4:00 PM, Tudor Girba <[email protected]> wrote: > How would you like to change Workspace? > > Doru > > > On Mon, May 19, 2014 at 2:56 PM, kilon alios <[email protected]>wrote: > >> a blog post could help a lot because I have no clue what systemLogger >> suppose to do or the other things. >> >> I was actually thinking enhancing Workspace. >> >> >> On Mon, May 19, 2014 at 3:49 PM, Sven Van Caekenberghe <[email protected]>wrote: >> >>> I am interested as well. >>> >>> I had some private discussions with Norbert and Doru, >>> and I used a different approach on one of my projects very recently >>> that I am quite happy with. >>> >>> BTW, I have long term plans to change ZnLogEvent... >>> >>> On 19 May 2014, at 14:31, Tudor Girba <[email protected]> wrote: >>> >>> > Me too. I already gave a first set of feedback. >>> > >>> > As a general matter, I would be interested in: >>> > - unifying with the ZnLogEvent >>> > - Split the Log class >>> > - Possibly support Fuel serialization for each log entry >>> > >>> > Doru >>> > >>> > >>> > On Mon, May 19, 2014 at 11:01 AM, [email protected] < >>> [email protected]> wrote: >>> > SystemLogger interests me as well. >>> > >>> > Phil >>> > >>> > >>> > On Mon, May 19, 2014 at 10:17 AM, Norbert Hartl <[email protected]> >>> wrote: >>> > Hi Stef, >>> > >>> > I’m definitely in for the SystemLogger. But as I am involved in it >>> anyway a fresh look from another person on that stuff could be benefitial. >>> > >>> > Norbert >>> > >>> > Am 19.05.2014 um 09:10 schrieb stepharo <[email protected]>: >>> > >>> > > Hi guys >>> > > >>> > > This is a call for some of you that committed code and would like to >>> do it with me :). >>> > > I have some projects that I would like to push further in 4.0 and >>> I'm thinking that >>> > > he could be much more fun to do it with other people. >>> > > >>> > > Here are some topics >>> > > - integrating the systemLogger >>> > > - integrating/improving the new method categorizer >>> > > - cleaning fonts >>> > > - ... >>> > > >>> > > How this could work? >>> > > We could have >>> > > - some discussions >>> > > - make a little roadmap >>> > > - then we could work on the same slice and do code review >>> > > >>> > > I think that it can be fun and motivating. So let me know because I >>> would like to have more social >>> > > coding. >>> > > >>> > > Stef >>> > > >>> > >>> > >>> > >>> > >>> > >>> > >>> > -- >>> > www.tudorgirba.com >>> > >>> > "Every thing has its own flow" >>> >>> >>> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >
