[coconParticipant]

Here is a component that combines a scroll bar and a label.

Monkey

Class LabelScrollbar Extends DockableView Field Caption:String Field Label:Label Field Scrollbar:ScrollBar Field OnValueChanged:Void(value:Int) Property Value:Int() Return Scrollbar.Value End Method New(caption:String, value:Int, min:Int, max:Int) Scrollbar = New ScrollBar Scrollbar.Minimum = min Scrollbar.Maximum = max Scrollbar.Value = value Scrollbar.ValueChanged = UpdateScrollbar Label = New Label Caption = caption UpdateLabel() AddView(Label, "top") AddView(Scrollbar, "top") End Private Method UpdateScrollbar(value:Int) UpdateLabel() OnValueChanged(value) End Method UpdateLabel() Label.Text = Caption + ": " + Scrollbar.Value End End

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42

Class LabelScrollbar Extends DockableView Field Caption:String Field Label:Label Field Scrollbar:ScrollBar Field OnValueChanged:Void(value:Int) Property Value:Int() Return Scrollbar.Value End Method New(caption:String, value:Int, min:Int, max:Int) Scrollbar                = New ScrollBar Scrollbar.Minimum        = min Scrollbar.Maximum        = max Scrollbar.Value          = value Scrollbar.ValueChanged   = UpdateScrollbar Label = New Label Caption = caption UpdateLabel() AddView(Label, "top") AddView(Scrollbar, "top")   End Private Method UpdateScrollbar(value:Int) UpdateLabel() OnValueChanged(value) End Method UpdateLabel() Label.Text = Caption + ": " + Scrollbar.Value End End

Monkey

Local radius := New LabelScrollbar("Radius", gProperties.ToolSpray_Radius, 1, 500) radius.OnValueChanged = Lambda(value:Int) gProperties.ToolSpray_Radius = value End Local density := New LabelScrollbar("Density", gProperties.ToolSpray_Density, 1, 500) density.OnValueChanged = Lambda(value:Int) gProperties.ToolSpray_Density = value End AddView(radius, "top") AddView(density, "top")

1 2 3 4 5 6 7 8 9 10 11

Local radius := New LabelScrollbar("Radius", gProperties.ToolSpray_Radius, 1, 500) radius.OnValueChanged = Lambda(value:Int) gProperties.ToolSpray_Radius = value End   Local density := New LabelScrollbar("Density", gProperties.ToolSpray_Density, 1, 500) density.OnValueChanged = Lambda(value:Int) gProperties.ToolSpray_Density = value End AddView(radius, "top") AddView(density, "top")

Attachments:

1. 

   mojox-label-scrollbar.png
   

[coconParticipant]

Oh, you ‘re saying that I would just use DockingView instead.

It seems that this is what works best.

Monkey

#import "<std>" #import "<mojo>" #import "<mojox>" Using std.. Using mojo.. Using mojox.. Class CustomView Extends DockingView Method New(a:String, b:String) Local b1 := New Button( a ) Local b2 := New Button( b ) AddView( b1 ,"top","50%" ) AddView( b2 ,"bottom","50%" ) End End Class MyWindow Extends Window Method New() Super.New( "DockingView Demo",640,480,WindowFlags.Resizable ) Local dockingView:=New DockingView dockingView.AddView( New CustomView("LEFT 1", "LEFT 2"),"left","50%" ) dockingView.AddView( New CustomView("RIGHT 1", "RIGHT 2"),"right","50%" ) ContentView=dockingView End End Function Main() New AppInstance New MyWindow App.Run() End

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

#import "<std>" #import "<mojo>" #import "<mojox>"   Using std.. Using mojo.. Using mojox..   Class CustomView Extends DockingView Method New(a:String, b:String) Local b1 := New Button( a ) Local b2 := New Button( b ) AddView( b1 ,"top","50%" ) AddView( b2 ,"bottom","50%" ) End End   Class MyWindow Extends Window   Method New() Super.New( "DockingView Demo",640,480,WindowFlags.Resizable ) Local dockingView:=New DockingView dockingView.AddView( New CustomView("LEFT 1", "LEFT 2"),"left","50%" ) dockingView.AddView( New CustomView("RIGHT 1", "RIGHT 2"),"right","50%" ) ContentView=dockingView End   End   Function Main() New AppInstance New MyWindow App.Run() End

Hopefully all of these snippets posted into this forum will be used to create a nice collection of examples.

[coconParticipant]

Hi Nerobot, I had a look at the monkey examples and I figured out that by looking at the “stargate.monkey2” example.

Monkey

#import "<std>" #import "<mojo>" #import "<mojox>" Using std.. Using mojo.. Using mojox.. Class CustomView Extends View Method New(a:String, b:String) Local dockingView := New DockingView dockingView.AddView( New Button( a ),"top","50%" ) dockingView.AddView( New Button( b ),"bottom","50%" ) AddView( dockingView ) End Method AddView( view:View ) AddChildView( view ) _views.Push( view ) End Method RemoveView( view:View ) RemoveChildView( view ) _views.Remove( view ) End Method OnLayout() Override For Local view:=Eachin _views view.Frame = Rect Next End Field _views:=New Stack<View> End Class MyWindow Extends Window Method New() Super.New( "DockingView Demo",640,480,WindowFlags.Resizable ) Local dockingView:=New DockingView dockingView.AddView( New CustomView("LEFT 1", "LEFT 2"),"left","50%" ) dockingView.AddView( New CustomView("RIGHT 1", "RIGHT 2"),"right","50%" ) ContentView=dockingView End End Function Main() New AppInstance New MyWindow App.Run() End

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59

#import "<std>" #import "<mojo>" #import "<mojox>"   Using std.. Using mojo.. Using mojox..   Class CustomView Extends View Method New(a:String, b:String) Local dockingView := New DockingView dockingView.AddView( New Button( a ),"top","50%" ) dockingView.AddView( New Button( b ),"bottom","50%" ) AddView( dockingView ) End Method AddView( view:View ) AddChildView( view ) _views.Push( view ) End Method RemoveView( view:View ) RemoveChildView( view ) _views.Remove( view ) End Method OnLayout() Override For Local view:=Eachin _views view.Frame = Rect Next End Field _views:=New Stack<View> End   Class MyWindow Extends Window   Method New() Super.New( "DockingView Demo",640,480,WindowFlags.Resizable ) Local dockingView:=New DockingView dockingView.AddView( New CustomView("LEFT 1", "LEFT 2"),"left","50%" ) dockingView.AddView( New CustomView("RIGHT 1", "RIGHT 2"),"right","50%" ) ContentView=dockingView End   End   Function Main()   New AppInstance New MyWindow App.Run() End

This is a reimplementation of what other GUI elements do, such as the Label or something else. For example instead of managing the stack with the views myself I found that I can extend the label and have the same idea.

I think that a new GUI element to be added to mojox, for example currently the hierarchy goes like this: View > Label, View > Button, then this new element would be done like this, View > ViewComponent.

How it should be named? i.e: ViewComponent, ViewNode, ViewControl, etc.

[coconParticipant]

Happy new year with lots of coding!

[coconParticipant]

It looks like this is the place where the users upload their stuff.
https://www.remix3d.com

[coconParticipant]

I would imagine only about repeating this concept about 20 times (for about a dozen of gui components). But for scalable code perhaps I will choose the architecture pattern instead. If in the future I will go that way I will post some new code.

[coconParticipant]

Doing a reverse image search revealed this:

[coconParticipant]

I have spotted various interesting websites offering tutorials.
http://www.emanueleferonato.com/
https://www.raywenderlich.com/
https://code.tutsplus.com/courses/search/Games
https://www.codeproject.com/search.aspx?q=game&x=0&y=0&sbo=kw

Other thing is from google search where it can lead you to more findings. But personally I have resulted into browsing code repositories and selected a few projects for long term studying (such as the Doom engines).
https://en.wikipedia.org/wiki/List_of_open-source_video_games

However be aware that in order for a tutorial to be easy to follow and study it must be offered as a “recipee” which is small and easy to follow. In order to get deeper into development you will need to get a proper book, and have persistency to follow it from beginning to the end. This is very important because it will take you through all of the aspects of the game, such as gameplay logic, saving-loading progress, level loading etc. One such book I got 5 years ago was this: Beginning iPhone Game Development (2010) which has all of the essential information for making a proper game. Unfortunately now is outdated, so it’s not of any immediate use – due to it was written for Cocos2D and Objective C, but form an academic standpoint the logic and information explained there is proper, it can be ported anywhere. I am sure that there might be other books, but I have not tried anything else, I can’t say for sure about something I don’t know.
vimeo.com/7352498

You can think of structuring the knowledge like this: You have the “Recipee” (how the game would look like while played). Then you will need to know the process of stacking a full codebase, how the game as it looks will stick into a larger finished project, these two go hand in hand.

[coconParticipant]

Happy holidays for all.

[coconParticipant]

I resulted into this sort of design. It looks a bit strange but there’s reason for doing it. I want to keep the entire model domain separated – and so on for the view domain. If I start to wrap my primitive datatypes with my own type system, I would probably connect the two domains in the core, while I want to connect them through a thin bridge.

Perhaps in this aspect you would assume I would simply have a manager function, with a beefed up select statement, that does straight value exchange from one place to the other. Well this is also one practical way of doing so, but for now it seems that this lambda approach gives the illusion of flexibility, because later I would create a Map-Database of such bindings ( Bindings:Map<String, Binding> ) in order to handle them by the large.

Monkey

' the class that binds two function callbacks Class Binding Field UpdateModel:Void() Field UpdateView:Void() End ' setting up the function callbacks bind.UpdateModel = Lambda() Data.Text = textfield.Text End bind.UpdateView = Lambda() textfield.Text = Data.Text End ' updating the model button.Clicked = Lambda() bind.UpdateModel() End ' updating the view Function SomethingHappens() bind.UpdateView() End

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

' the class that binds two function callbacks Class Binding Field UpdateModel:Void() Field UpdateView:Void() End   ' setting up the function callbacks bind.UpdateModel = Lambda() Data.Text = textfield.Text End   bind.UpdateView = Lambda() textfield.Text = Data.Text End   ' updating the model button.Clicked = Lambda() bind.UpdateModel() End   ' updating the view Function SomethingHappens() bind.UpdateView() End

Lately I have started becoming anti-object oriented, that’s why I try to find functional or metaprogramming-reflection alternatives. In order to minimize declarations and such. However perhaps creating a full project that scales predictably perhaps needs a more streamlined approach as you suggest.

[coconParticipant]

For the iPad vs iPhone debate, I would consider these to be two different categories of products. You will have to think at where people use each device and try to think how your application will fit into these patterns. So grabbing such device will help you get into the testing your application as a simple user.

For building applications, you test anything in the emulator, such as old iOS versions, different devices. Then you can do test deployments up to 5 of your devices. However when you try to release something to the app store things change and the developer account needs to be purchased.
https://apple.stackexchange.com/questions/206123/xcode-7-develop-for-ios-without-developer-account

P.S. Currently I have an iPhone 4 which is the one I am stuck for now. However I am very happy with it, despite the fact that it very old, for using a dozen of specific applications it works fine (i.e. Nanostudio). If I were to purchase a newer model I would go for the iPhone 7 or 8, and only for keeping up with the OS versioning, not so much for the latest hardware features etc.

[coconParticipant]

OK I figured out.

If anyone is interested to use it, perhaps to be added in the mojox tests.

Monkey

Namespace myapp #Import "<std>" #Import "<mojo>" #Import "<mojox>" Using std.. Using mojo.. Using mojox.. Class CanvasView Extends View Method OnRender(canvas:Canvas) Override canvas.DrawLine(0, 0, Mouse.X, Mouse.Y) End Method OnMouseEvent(event:MouseEvent) Override App.RequestRender() End End Class MyWindow Extends Window Field mainDock :DockingView Field toolsDock :DockingView Field canvasView :CanvasView Method New() Super.New("Paint Application", 1280, 720) mainDock = New DockingView toolsDock = New DockingView canvasView = New CanvasView Local button := New Button("Button 1") toolsDock.AddView(button, "top") mainDock.AddView(toolsDock, "right", 100) mainDock.ContentView = canvasView ContentView = mainDock End End Function Main() New AppInstance New MyWindow App.Run () End

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51

Namespace myapp   #Import "<std>" #Import "<mojo>" #Import "<mojox>"   Using std.. Using mojo.. Using mojox..   Class CanvasView Extends View Method OnRender(canvas:Canvas) Override canvas.DrawLine(0, 0, Mouse.X, Mouse.Y) End Method OnMouseEvent(event:MouseEvent) Override App.RequestRender() End End   Class MyWindow Extends Window   Field mainDock   :DockingView Field toolsDock  :DockingView Field canvasView :CanvasView Method New() Super.New("Paint Application", 1280, 720)   mainDock    = New DockingView toolsDock   = New DockingView canvasView  = New CanvasView Local button := New Button("Button 1") toolsDock.AddView(button, "top") mainDock.AddView(toolsDock, "right", 100) mainDock.ContentView = canvasView ContentView = mainDock End End   Function Main() New AppInstance New MyWindow App.Run () End

[coconParticipant]

I tried the Admin technique but nothing happened. But anyway. Trying to see what happens with this dialog, I mentioned it here so Mark can see it.

RequestFile can't display C:WindowsFonts

[coconParticipant]

Testing something…

X Escaping the character using the preformatted – by opening and closing double grave accent

√ Escaping the character ` inside a code html block

X Trying to insert the HTML character id inside the code tag (& # 9 6 <– these are joined, not spaced)
&#96

[coconParticipant]

nerobot, as I try to change the font, I press the button […] the file browser dialog pops up nicely. I try to navigate to C:\Windows\Fonts but there the directory is inaccessible (it tries to render the fonts as it wants with this viewer, instead of displaying simple file list). The workaround is to copy the font from the Windows Fonts location to something else.

Another option is to leave the textbox value open, so I can copy paste the location directly.

[Author]

Posts