69 skills found · Page 1 of 3
BlackyHawky / ClockCustomizable, privacy‑first, open-source clock app inspired by AOSP Clock
ShawnWhite666 / HTimerHonor has a large number of scheduled and periodic tasks that need to be processed on time. Htimer is a microservice system developed in Java, designed to function as an alarm clock service within the microservices architecture. It supports high precision and high load scheduling requirements.
WebDevSimplified / JavaScript ClockNo description available
lianghuan-xatu / Jd Pruchase Kill DevThis project focuses on optimizing the Java version of JD.com’s Moutai flash sale system, including error time adjustment and queue process optimization. The program compares local time with JD.com’s server time and adjusts accordingly, ensuring that the purchase timing is based on the local system’s clock.
im-pro-at / WordClockGeneratorJava program to generate a Word Clock text matrix
felipeAguiarCode / Java Clock EcommerceBuild Java API
stawirej / TimeflowProvides java clock which can be adjusted in tests without using dependency injection.
shrestha-bishal / BankoneerCompleteBankingSystemCoreBANKONEER (A Co-operative Banking System Software with Online Banking) [JAVA, PHP, HTML & CSS, JS, MS-SQL With ODBC-Connector Driver] BANKONEER, a Co-operative Banking System Software for handling transactions carried in co-operative banks daily in a computerized manner & to nurture the needs of an end banking by providing various ways to perform banking tasks with different departments as CEO, account, loan, e-banking, cashier and online banking. BANKONEER system comes in three platforms as Desktop Workstation software used in co-operative administrative and administration (JAVA platform & framework), Online Banking for members of co-operative banks (PHP, HTML, CSS & JS with ODBC connector driver) & MS-SQL (server). The system is designed with simple GUI for effective user interaction and increased effectiveness for handling the transactions and flow of the financials in a computerized manner with sophisticated algorithms. With Online Banking the members of the co-operative banks can be transparent. Also the features like Transactions, Loans Details (on-going & completed) & the installments, Third-Party Transfer, Wallet Concept etc. have made the software stand-out. The system deals with data entry, validation & confirmation, handling transactions and financials flow, updating etc. We have also developed our own Online Payment Portal ‘B-Payment’ and embedded it with BANKONEER for third-party transfer. Thus BANKONEER designed according to the specifications & requirements saves transaction time, increase efficiency & also makes the bond between co-operative banks and its members stronger. “BANKONEER, Co-operative Banking System Software with Online Banking” project is a model desktop application and internet banking site for complete cooperative banking transactions and to maintain all related issues in very efficient manner in computerized way. This project enables both bank staffs to handle day to day co-operative banking operations and costumers to perform the basic banking transactions through online too. This system provides banking operations handling to banking staff at one end whereas the access to the customer to create an account, deposit/withdraw the cash from account, third-party transfers, wallet and also to view reports of all accounts, transactions and loan details(on-going and completed) at the other end. The customers can access the banks website for viewing their account details and perform the transactions on account as per their requirements. The simple GUI (Graphical User Interface) in desktop application makes it user friendly and efficient to handle all the transactions for admins or staffs. Bank administrative have full control over the system as they can add, remove, manage transactions/financials and manage other utilities. Customers can also make account form their home with required paperwork and verifications from administrative. With this system the brick and mortar structure of traditional co-operative banking gets converted into a click and portal model, thereby giving a concept of virtual banking a real shape in our sole purpose. E-banking/Online Banking facilitates banking transactions by members round the clock globally. The primary aim of this project is to provide an improved design methodology which envisages the future expansions and modification necessary for the core sector like banking. This necessitates the design to be expandable and modifiable and so a modular approach in this bank can become a member of banking system.
PhongPham101190 / Red C SDKMEGA SDK - Client Access Engine Coverity Scan Build Status MEGA --- The Privacy Company --- is a Secure Cloud Storage provider that protects your data thanks to end-to-end encryption. We call it User Controlled Encryption, or UCE, and all our clients automatically manage it. All files stored on MEGA are encrypted. All data transfers from and to MEGA are encrypted. And while most cloud storage providers can and do claim the same, MEGA is different – unlike the industry norm where the cloud storage provider holds the decryption key, with MEGA, you control the encryption, you hold the keys, and you decide who you grant or deny access to your files. This SDK brings you all the power of our client applications and let you create your own or analyze the security of our products. Are you ready to start? Please continue reading. SDK Contents In this SDK, you can find our low level SDK, that was already released few months after the MEGA launch, a new intermediate layer to make it easier to use and to bind with other programming languages, and example apps for all our currently supported platforms (Windows, Linux, OSX, Android, iOS and Windows Phone). In the examples folder you can find example apps using: The low level SDK: megacli (a powerful command line tool that allows to use all SDK features) megasimplesync (a command line tool that allows to use the synchronization engine) The intermediate layer: An example app for Visual Studio in examples/win32 An example app for Android (using Java bindings based on SWIG) in examples/android An example app for iOS (using Objective-C bindings) in examples/iOS An example app for Windows Phone (using Windows Phone bindings) in examples/wp8 Building If you plan to develop an app using this SDK, please use the stable branch or the last released tarball. The master branch is continuously evolving, could be unstable and could change very often. For platforms with Autotools, the generic way to build and install it is: sh autogen.sh ./configure make sudo make install That compilation will include the examples using our low level SDK (megacli and megasimplesync) You also have specific build instructions for OSX (doc/OSX.txt) and FreeBSD (doc/FreeBSD.txt) and a build script to automatically download and build the SDK along with all its dependencies (contrib/build_sdk.sh) For other platforms, or if you want to see how to use the new intermediate layer, the easiest way is to get a smooth start is to build one of the examples in subfolders of the examples folder. All these folders contains a README.md file with information about how to get the project up and running, including the installation of all required dependencies. Usage The low level SDK doesn't have inline documentation yet. If you want to use it, please check one of our example apps (examples/megacli, examples/megasimplesync). The new intermediate layer has been documented using Doxygen. The only public header that you need to include to use is include/megaapi.h. You can read the documentation in that header file, or download the same documentation in HTML format from this link: https://mega.co.nz/#!c5FzhBJL!HUVjsOJTylwkmXPZ0AxT66Wuu4YvZInyHbWGYgvTHt4 Additional info Platform Dependencies Dependencies are different for each platform because the SDK uses generic interfaces to get some features and they have different implentations: Network (cURL with OpenSSL/c-ares or WinHTTP) Filesystem access (Posix or Win32) Graphics management (FreeImage, QT or iOS frameworks) Database (SQLite or Berkeley DB) Threads/mutexes (Win32, pthread, QT threads, or C++11) POSIX (Linux/Darwin/BSD/OSX ...) Install the following development packages, if available, or download and compile their respective sources (package names are for Debian and RedHat derivatives, respectively): cURL (libcurl4-openssl-dev, libcurl-devel), compiled with --enable-ssl c-ares (libc-ares-dev, libcares-devel, c-ares-devel) OpenSSL (libssl-dev, openssl-devel) Crypto++ (libcrypto++-dev, libcryptopp-devel) zlib (zlib1g-dev, zlib-devel) SQLite (libsqlite3-dev, sqlite-devel) or configure --without-sqlite FreeImage (libfreeimage-dev, freeimage-devel) or configure --without-freeimage pthread Optional dependency: Sodium (libsodium-dev, libsodium-devel), configure --with-sodium Filesystem event monitoring: The provided filesystem layer implements the Linux inotify and the MacOS fsevents interfaces. To build the reference megacli example, you may also need to install: GNU Readline (libreadline-dev, readline-devel) For Android, we provide an additional implementation of the graphics subsystem using Android libraries. For iOS, we provide an additional implementation of the graphics subsystem using Objective C frameworks. Windows To build the client access engine under Windows, you'll need the following: A Windows-native C++ development environment (e.g. MinGW or Visual Studio) Crypto++ zlib (until WinHTTP learns how to deal with Content-Encoding: gzip) SQLite or configure --without-sqlite FreeImage or configure --without-freeimage pthreads (MinGW) Optional dependency: Sodium or configure --with-sodium To build the reference megacli.exe example, you will also need to procure development packages (at least headers and .lib/.a libraries) of: GNU Readline/Termcap Folder syncing In this version, the sync functionality is limited in scope and functionality: There is no locking between clients accessing the same remote folder. Concurrent creation of identically named files and folders can result in server-side dupes. Syncing between clients with differing filesystem naming semantics can lead to loss of data, e.g. when syncing a folder containing ABC.TXT and abc.txt with a Windows client. On POSIX platforms, filenames are assumed to be encoded in UTF-8. Invalid byte sequences can lead to undefined behaviour. Local filesystem items must not be exposed to the sync subsystem more than once. Any dupes, whether by nesting syncs or through filesystem links, will lead to unexpected results and loss of data. No in-place versioning. Deleted remote files can be found in //bin/SyncDebris (only when syncing to the logged in account's own cloud drive - there is no SyncDebris facility on syncs to inbound shares), deleted local files in a sync-specific hidden debris folder located in the local sync's root folder. No delta writes. Changed files are always overwritten as a whole, which means that it is not a good idea to sync e.g. live database tables. No direct peer-to-peer syncing. Even two machines in the same local subnet will still sync via the remote storage infrastructure. No support for unidirectional syncing (backup-only, restore-only). Syncing to an inbound share requires it to have full access rights. megacli on Windows The megacli example is currently not handling console Unicode input/output correctly if run in cmd.exe. Filename caveats: Please prefix all paths with \\?\ to avoid the following issues: The MAX_PATH (260 character) length limitation, which would make it impossible to access files in deep directory structures Prohibited filenames (con/prn/aux/clock$/nul/com1...com9/lpt1...lpt9). Such files and folders will still be inaccessible through e.g. Explorer! Also, disable automatic short name generation to eliminate the risk of clashes with existing short names.
jbrisbin / Reactor Ntp Clockjava.time.Clock implementation that uses NTP and a Reactor Flux to manage the current time
Iqbolshoh / Javascript Digital Clock⏰ A sleek, responsive javascript-digital-clock built with HTML, CSS, and JavaScript. Shows current time 🕒 with smooth updates ⏳ and adapts to all screens 📱. Perfect for stylish real-time time display! 💻📲
sefyudem / JavaScript Analog ClockNo description available
mattzeunert / Javascript Clock SpeedupSimulate a faster Date object for debugging purposes.
state-machine-systems / Mock ClockA mock Clock implementation for Java 8
tuvtran / LamportClockImplementation of Lamport Clock in Java
varunu28 / Vector ClockAn implementation of Vector Clock in Java :alarm_clock:
eventreducer / HlcHybrid Logical Clocks for Java
milsaware / Javascript Clock Patience SolitaireA fully playable, no images, vanilla Javascript and CSS Clock Patience Solitaire Game. Free to download, free to play, free to recycle.
Siddarth305 / Digital Clock Using JAVANo description available
shaweiwei / Happy Chat≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈ 【软件名称】HappyChat聊天室 【最新版本】1.0 【运行平台】Windows 9X/ME/2K/XP 【软件简介】一个非常好用的聊天室。 ≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈ 本聊天室是一个多用户的聊天室。包括：用户注册、注册资料保存、用户登陆、 核对用户名和用户密码、多用户登录、多用户同聊、私聊、保存用户记录、用户 离开记录自动清除、在线人数监视等多种功能。 使用方法： 1.服务器端:运行服务器程序 2.客户端: (1)启动聊天室，输入Ip地址以登陆服务器。 (2)进入登陆界面，第一次登陆需要注册，点注册按扭。 (3)按要求填完注册信息。 (4)返回登陆窗口，输入用户名、密码，进行登陆。 (5)进入聊天室。。 进入聊天室后，就可以尽情的聊天了，可以和你喜欢的人私聊了，聊的开心 话题还可以进行保存，当然，你也可以清屏。 ≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈ 程序编译顺序: 服务器程序:ServerFrame.java-->AppServer.java 客户端程序:ChatClient.java-->Register.java-->Login.java-->Clock.java-->ChatRoom.java
