Login System/ Windows Emulator

This is just a small demo showing my custom login system.
By default you are NOT registered. You can register an account once you are logged in on the Greenfoot website. You define a password that can be reset later, if you are logged in on the website.

PASSWORD:
DON'T USE A PASSWORD YOU USE ELSEWHERE! The password IS hashed in a simple way, however the auther can look at that value.

Once you have an account you can log in using your normal username and the created password. You can now also log in from another account or without being logged in at all.

Once logged in you can test my (so far not very advanced) Windows 10 emulator. Its (only) feature is the fully functional window system. You can drag the window, fullscreen it with the button or by double-clicking the top bar, and scale it by dragging the borders.

About the drawing system:

This scenario uses my custom widget system. This means that the whole screen is actually just a single actor. The image that shows the widget and animations is (efficiently) drawn completly customly and is not bound to any Greenfoot draw order system.
It is loosely based on the widget system of Flutter, which is used for android apps.

Like usually, everything is 100% reusable. The widgets may take some time to get used to though and will not be nice to code inside the Greenfoot editor, which is one of the reasons why I`'m using VSCode.

4139 views / 8 in the last 7 days

10 votes | 0 in the last 7 days

Tags: mouse demo with-source button windows login widgets flutter

This scenario is a member of: Reusable classes

Embed | View applet version

2021/2/19

2021/2/19

2021/2/19

2021/4/12

By the way what is resuable U use this word in lot many places And i have downloaded some of ur scenarios but they show some errors and all of ur scenarios where without 'myWorld'

RcCookie

2021/4/13

Reusable means that you have some classes, in this case widgets which make up the ui, and you can rearrange them however you want. The login menu is really more a demo of what can be done with it. Another example would be the raycasting scenario, where you can see visually how the ray casting works, but you can use the underlying ray cast system in any scenario. What you may find is that these classes are not visible if you open the scenario in Greenfoot. Just like you need to import the Greenfoot stuff with „import greenfoot.*;“ you need to import my stuff, for example „import com.github.rccookie.greenfoot.game.raycast.*;“. This is certainly a bit longer but normal for java. A package basically describes the folder in which the file is located. That is why you will find exactly that folder structure in my scenarios. Concerning „MyWorld“, that’s because of two things: 1. You don’t have to name your world „MyWorld“, and I never do 2. I am not actually extending World directly, which is why you ain’t see my world class under World. What I actually do is extend a class that is also part of my library which that is extending the World class.